113 A error occured while adding a e-mail address.
114 A error occured while adding a messenger address.
115 A error occured while adding a snoozed note.
116 A error occured while adding a layer.
117 A error occured while adding a calendar note.
118 A error occured while adding a task.
119 A error occured while adding a alarm.
120 A error occured while adding settings.
121 Error opening data base.
122 Process aborted by user.
123 Error writing calendar icon.
124 Wrong version. Supporting only version 6.7 and lower.
125 /detect - see whether ADC is installed and\n begin migration if neccessery\n/quit - stop running ADC instance\n/service - enter maintenance mode\n/extract <path> - extracts old archived\n data to specified folder\n if ommited extracts to original folder\n\nSwitches used with /detect:\n/deldb - deletes records form DB\n/delold - deletes files after migration\n/log - enable logging
126 A error occured while adding a desktop picture.
127 Data Migration Warning\n=================\n\nWARNING! You are upgrading your Active Desktop Calendar to a version with\nnew data engine. This requires that all data you currently have in the\nprogram migrate from separate files representing calendar data layers and\ncontacts to a single relational database file. \n\nTHIS OPERATION CAN NOT BE UNDONE! THEREFORE AFTER DATA MIGRATION COMPLETES\nYOU WILL NOT BE ABLE TO GO BACK TO AN OLDER VERSION OF THE PROGRAM AND KEEP\nOLD DATA. \n\nHere is what exactly happens during data migration process: \n - all data from local calendar layers are transferred to the new database\nfile. \n - all external calendar layers (LAN, Outlook, Google, Web) are transferred\nto the database empty of their data, so you will have to wait for the next\nscheduled update or give an explicit Refresh command to get data for those\nlayers again. (this may be a problem only for external layers where source) \n - all contacts are also transferred to the database. \n - upon successful migration all transferred data files that belong to the\nold version are archived into a single backup file with extension .XARC and\ndeleted afterwards. \n - you get a data migration summary report. \n - in case the data migration is not completed for any reason you will get\na report about that and the installation of the new version will stop; you\nwill remain with the old version of the program and all its data intact. \n\nWHILE EVERY PRECAUTION IS TAKEN THAT THERE IS NO LOSS OF DATA DURING THE\nMIGRATION PROCESS IF IN ANY DOUBT YOU CAN CANCEL THE INSTALLATION NOW AND\nREMAIN WITH THE OLD VERSION OF THE PROGRAM. \nIF YOU DECIDE TO GO THROUGH THE MIGRATION PROCESS YOU HAVE TO ASSUME FULL\nRESPONSIBILITY FOR YOUR DATA.
128 Unfortunately migration of your calendar data did not succeed. Please look for the ADCmigrationReport.txt file on on your desktop, send it to XemiComputers Technical Support at info@xemico.com and describe what happened. \n\nFailure on data migration process also means that the new version of the program could not have been installed. You will remain with the old version and all its data intact.
129 Active Desktop Calendar setup successfully migrated your calendar data to the new database file. If you want to see the detailed report about this process look for the ADCmigrationReport.txt file in the program's default data folder: \n%appFolder%Log\n\nPlease click CONTINUE button below to finalize installation of the new version.
130 Error creating log file.
131 Error creating archive file.
132 Error deleting old data files.
133 Error opening data file
134 The registry key for ADC seems to be corrupt.
135 Active Desktop Calendar setup could not migrate your calendar data to the\nnew database file due to invalid contents of the system registry so no data\nwere found. Setup will now continue and you will get the new version of the\nprogram with empty database file. Please look for the ADCmigrationReport.txt file on your desktop, send it to XemiComputers Technical Support at info@xemico.com and describe what happened.
136 Error deleting file
137 Error opening data base.
138 {\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}{\f1\fswiss\fcharset0 Arial;}{\f2\fnil\fcharset2 Symbol;}}{\colortbl ;\red255\green0\blue0;}{\*\generator Msftedit 5.41.15.1507;}\viewkind4\uc1\pard\sb100\sa100\b\f0\fs28 Data Migration Warning\line\fs24\par\b0\fs18\line\cf1\b\fs20 WARNING!\cf0\b0 \fs18 You are upgrading your Active Desktop Calendar to a version with\line new data engine. This requires that all data you currently have in the program\line migrate from separate files representing calendar data layers and contacts to\line a single relational database file.\par\b THIS OPERATION CAN NOT BE UNDONE! THEREFORE AFTER DATA\line MIGRATION COMPLETES YOU WILL NOT BE ABLE TO GO BACK TO AN\line OLDER VERSION OF THE PROGRAM AND KEEP OLD DATA.\par\b0 Here is what exactly happens during data migration process:\par\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-180\li180\sb100\sa100 all data from local calendar layers are transferred to the new database\line file.\par{\pntext\f2\'B7\tab}all external calendar layers (LAN, Outlook, Google, Web) are transferred\line to the database empty of their data, so you will have to wait for the next\line scheduled update or use the explicit Refresh command to get data for\line those layers again. (this may be a real problem only for external layers\line where source file/location is no longer available)\par{\pntext\f2\'B7\tab}all contacts are also transferred to the database.\par{\pntext\f2\'B7\tab}upon successful migration all transferred data files that belong to the\line old version are archived into a single backup file with extension .XARC\line and deleted afterwards.\par{\pntext\f2\'B7\tab}in case the data migration is not completed for any reason you will get\line a report about that and the installation of the new version will stop; you\line will remain with the old version of the program and all its data intact.\par{\pntext\f2\'B7\tab}data migration log file is created in all cases.\par\pard\sb100\sa100\b WHILE EVERY PRECAUTION IS TAKEN THAT THERE IS NO LOSS OF DATA\line DURING THE MIGRATION PROCESS, IF IN ANY DOUBT YOU CAN CANCEL\line THE INSTALLATION NOW AND REMAIN WITH THE OLD VERSION OF THE\line PROGRAM.\par IF YOU DECIDE TO GO THROUGH THE MIGRATION PROCESS YOU HAVE\line TO ASSUME FULL RESPONSIBILITY FOR YOUR DATA.\par\pard\b0\f1\fs20\par}
139 Error deleting folder
140 Error creating folder '%s', reason: %s
61440 Open
61441 Save As
61442 All Files (*.*)
61443 Untitled
61446 an unnamed file
61457 &Hide
61472 No error message is available.
61473 An unsupported operation was attempted.
61474 A required resource was unavailable.
61475 Out of memory.
61476 An unknown error has occurred.
61477 An invalid argument was encountered.
61696 Invalid filename.
61697 Failed to open document.
61698 Failed to save document.
61699 Save changes to %1?
61700 Failed to create empty document.
61701 The file is too large to open.
61702 Could not start print job.
61703 Failed to launch help.
61704 Internal application error.
61705 Command failed.
61706 Insufficient memory to perform operation.
61707 System registry entries have been removed and the INI file (if any) was deleted.
61708 Not all of the system registry entries (or INI file) were removed.
61709 This program requires the file %s, which was not found on this system.
61710 This program is linked to the missing export %s in the file %s. This machine may have an incompatible version of %s.
61712 Please enter an integer.
61713 Please enter a number.
61714 Please enter an integer between %1 and %2.
61715 Please enter a number between %1 and %2.
61716 Please enter no more than %1 characters.
61717 Please select a button.
61718 Please enter an integer between 0 and 255.
61719 Please enter a positive integer.
61720 Please enter a date and/or time.
61721 Please enter a currency.
61722 Please enter a GUID.
61723 Please enter a time.
61724 Please enter a date.
61728 Unexpected file format.
61729 %1\nCannot find this file.\nPlease verify that the correct path and file name are given.
61730 Destination disk drive is full.
61731 Unable to read from %1, it is opened by someone else.
61732 Unable to write to %1, it is read-only or opened by someone else.
61733 An unexpected error occurred while reading %1.
61734 An unexpected error occurred while writing %1.
61744 %1: %2\nContinue running script?
61745 Dispatch exception: %1
61836 Unable to read write-only property.
61837 Unable to write read-only property.
61840 Unable to load mail system support.
61841 Mail system DLL is invalid.
61842 Send Mail failed to send message.
61856 No error occurred.
61857 An unknown error occurred while accessing %1.
61858 %1 was not found.
61859 %1 contains an invalid path.
61860 %1 could not be opened because there are too many open files.
61861 Access to %1 was denied.
61862 An invalid file handle was associated with %1.
61863 %1 could not be removed because it is the current directory.
61864 %1 could not be created because the directory is full.
61865 Seek failed on %1
61866 A hardware I/O error was reported while accessing %1.
61867 A sharing violation occurred while accessing %1.
61868 A locking violation occurred while accessing %1.
61869 Disk full while accessing %1.
61870 An attempt was made to access %1 past its end.
61872 No error occurred.
61873 An unknown error occurred while accessing %1.
61874 An attempt was made to write to the reading %1.
61875 An attempt was made to access %1 past its end.
61876 An attempt was made to read from the writing %1.
